Release 10.1A: OpenEdge Development:
Messaging and ESB
setErrorHandler procedure
Sets the error-handling procedure.
Syntax
Applies to
Session objects
Notes
- The application must create the error-handling
messageConsumerobject and call the setErrorHandler procedure after calling the beginSession procedure. If the application does not call the setErrorHandler procedure, a default error handler displays the error message and the properties in alert boxes.- The application should handle asynchronously reported error conditions programmatically by creating an error-handling Message Consumer object and passing it to the setErrorHandler procedure in the Session object. The setErrorHandler procedure creates an error-handling Message Consumer object.
- Asynchronous conditions are always reported as a
TextMessagewith several possibleCHARACTERmessage properties. TheCHARACTERproperties that might be included in the message header are:exception,errorCode,linkedException-1,linkedException-2 … linkedException-n(wherenis a number of additional exceptions linked to the main exception).- The getPropertyNames function can be used to get the list of properties in the error message header.
See also
setErrorHandler procedure, setNoErrorDisplay procedure
For more information, see the "Error and condition handling" section. For an example, see the Appendix B "Messaging Examples."
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |